I have some questions on which approch to take with the HF macros.

Should they keep the current string input or take functions directly as
input? Taking functions directly is how the macros were originally intended,
but the string method makes it possible to also use macros as input which
makes some things possible that can't be done with functions.

Should they take the input height data from a standard 2d square from <0,0>
to <1,1> (like UV mapping and like the height_field object works) or should
they take the height data from the points in 3D space where the surface is
(just like a solid texture works)? If the latter is decided, I think they
should be named to something else than HF_*, as it is inconsistent with the
basic concept of the height_field object. It's more like displacement
mapping.

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:    http://rsj.mobilixnet.dk (updated Feb 16)
POV-Ray Users:   http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk

Post a reply to this message